Markup Validation Service

Validation Output: 450 Errors

1. Line 24, Column 47: end tag for "meta" omitted, but OMITTAG NO was specified

   …="y_key" content="1d8b62e6da1997a…

   ✉

   You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

2. Line 24: start tag was here

   ><meta name="y_key" content="1d8b62e6da1997ab">

3. Line 169, Column 299: character "&" is the first character of a delimiter but occurred as data

   …type="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServ

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
4. Line 169, Column 300: character "&amp;" is the first character of a delimiter but occurred as data

   …ype="text/javascript">    if (!nad && typeof(window["GS_googleAddAdSenseServi

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
5. Line 244, Column 31: an attribute value must be a literal unless it contains only name characters

   document.writeln('<style type=\"text/css\">');

   ✉

   You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

6. Line 244, Column 43: document type does not allow element "style" here

   document.writeln('<style type=\"text/css\">');

   ✉

   The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

   One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

7. Line 328, Column 71: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

   …" class="txt" type="text" value="" /> <a onclick="if ($('#txt_searchBox')[0].

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

8. Line 328, Column 187: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

   …('#fm_Search').submit();};" href="#"><img alt="Search" src="/gfx/00/07/40/bt-

   ✉

   The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

   One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

9. Line 1012, Column 82: character "&amp;" is the first character of a delimiter but occurred as data

   …chedule---results/" title="Schedule & Results">Schedule & Results</a></li>

   ✉

   This message may appear in several cases:

   • You tried to include the "<" character in your page: you should escape it as "&lt;"
   • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
   • Another possibility is that you forgot to close quotes in a previous tag.
10. Line 1012, Column 102: character "&amp;" is the first character of a delimiter but occurred as data

    …title="Schedule & Results">Schedule & Results</a></li>

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
11. Line 1116, Column 20: Attribute "language" exists, but can not be used for this element.

    		<script language="JavaScript" type="text/javascript">

    ✉

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

12. Line 1123, Column 28: an attribute value must be a literal unless it contains only name characters

    document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

13. Line 1123, Column 57: "height:" is not a member of a group specified for any attribute

    … style=\"position:relative; height: 293px;\"><div style=\"position:absolute; 

    ✉

14. Line 1123, Column 57: "293px" is not a member of a group specified for any attribute

    … style=\"position:relative; height: 293px;\"><div style=\"position:absolute; 

    ✉

15. Line 1123, Column 65: document type does not allow element "div" here

    …"position:relative; height: 293px;\"><div style=\"position:absolute; left: -1

    ✉

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

16. Line 1123, Column 77: an attribute value must be a literal unless it contains only name characters

    …:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

    ✉

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

17. Line 1123, Column 104: "left:" is not a member of a group specified for any attribute

    …iv style=\"position:absolute; left: -19px;\">");

    ✉

18. Line 1123, Column 104: "-19px" is not a member of a group specified for any attribute

    …iv style=\"position:absolute; left: -19px;\">");

    ✉

19. Line 1270, Column 170: required attribute "alt" not specified

    …/17/96794431-10_50imgGalTh-IC.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

20. Line 1402, Column 292: required attribute "alt" not specified

    …/20/96798599-10_50imgGalTh-eH.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

21. Line 1411, Column 354: required attribute "alt" not specified

    …/20/96798841-10_52imgGalTh-jL.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

22. Line 1420, Column 262: required attribute "alt" not specified

    …/20/96798502-10_56imgGalTh-Ct.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

23. Line 1429, Column 217: required attribute "alt" not specified

    …/28/20/96797369_58imgGalTh-XH.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

24. Line 1438, Column 215: required attribute "alt" not specified

    …/28/20/96797141_60imgGalTh-nk.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

25. Line 1447, Column 226: required attribute "alt" not specified

    …/20/96798329-10_26imgGalTh-Oh.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

26. Line 1466, Column 260: required attribute "alt" not specified

    …/20/96797665-10_24imgGalTh-oZ.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

27. Line 1475, Column 227: required attribute "alt" not specified

    …/28/19/96795338_38imgGalTh-DX.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

28. Line 1484, Column 227: required attribute "alt" not specified

    …/28/19/96795303_34imgGalTh-Nz.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

29. Line 1493, Column 239: required attribute "alt" not specified

    …/28/19/96795261_40imgGalTh-eP.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

30. Line 1502, Column 247: required attribute "alt" not specified

    …/28/19/96795304_32imgGalTh-fq.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

31. Line 1511, Column 229: required attribute "alt" not specified

    …/28/19/96797297_04imgGalTh-gC.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

32. Line 1530, Column 229: required attribute "alt" not specified

    …/28/19/96797236_06imgGalTh-UN.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

33. Line 1539, Column 227: required attribute "alt" not specified

    …/28/19/96797221_28imgGalTh-gr.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

34. Line 1548, Column 222: required attribute "alt" not specified

    …/19/96797178-10_26imgGalTh-kS.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

35. Line 1557, Column 210: required attribute "alt" not specified

    …/19/96797129-10_24imgGalTh-gs.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

36. Line 1566, Column 179: required attribute "alt" not specified

    …/28/19/96731852_36imgGalTh-xk.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

37. Line 1575, Column 248: required attribute "alt" not specified

    …/19/96797106-10_22imgGalTh-ZR.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

38. Line 1594, Column 250: required attribute "alt" not specified

    …/19/96796234-10_20imgGalTh-Ak.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

39. Line 1603, Column 260: required attribute "alt" not specified

    …/19/96795409-10_16imgGalTh-aE.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

40. Line 1612, Column 208: required attribute "alt" not specified

    …/19/96796113-10_18imgGalTh-ND.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

41. Line 1621, Column 272: required attribute "alt" not specified

    …/19/96795248-10_14imgGalTh-cr.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

42. Line 1630, Column 202: required attribute "alt" not specified

    …/19/96795021-10_10imgGalTh-AM.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

43. Line 1639, Column 190: required attribute "alt" not specified

    …/19/96794741-10_02imgGalTh-ad.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

44. Line 1658, Column 215: required attribute "alt" not specified

    …/28/19/96796362_00imgGalTh-eO.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

45. Line 1667, Column 215: required attribute "alt" not specified

    …/28/18/96795803_96imgGalTh-Iz.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

46. Line 1676, Column 231: required attribute "alt" not specified

    …/28/18/96795879_86imgGalTh-Lz.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

47. Line 1685, Column 231: required attribute "alt" not specified

    …/28/18/96796044_88imgGalTh-Ay.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

48. Line 1694, Column 233: required attribute "alt" not specified

    …/28/18/96796327_90imgGalTh-wv.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

49. Line 1703, Column 239: required attribute "alt" not specified

    …/28/18/96796523_92imgGalTh-YP.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

50. Line 1761, Column 65: cannot generate system identifier for general entity "utm_medium"

    …r2010.com/store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_con

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

51. Line 1761, Column 65: general entity "utm_medium" not defined and no default entity

    …r2010.com/store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_con

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

52. Line 1761, Column 75: reference not terminated by REFC delimiter

    …store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

53. Line 1761, Column 75: reference to external entity in attribute value

    …store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

54. Line 1761, Column 75: reference to entity "utm_medium" for which no system identifier could be generated

    …store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" t

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

55. Line 1761, Column 63: entity was defined here

    …ver2010.com/store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_c

56. Line 1761, Column 83: cannot generate system identifier for general entity "utm_source"

    …tm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="Le

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

57. Line 1761, Column 83: general entity "utm_source" not defined and no default entity

    …tm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="Le

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

58. Line 1761, Column 93: reference not terminated by REFC delimiter

    …n=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Game

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

59. Line 1761, Column 93: reference to external entity in attribute value

    …n=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Game

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

60. Line 1761, Column 93: reference to entity "utm_source" for which no system identifier could be generated

    …n=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Game

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

61. Line 1761, Column 81: entity was defined here

    …?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" title="

62. Line 1761, Column 99: cannot generate system identifier for general entity "utm_content"

    …r&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Games Begi

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

63. Line 1761, Column 99: general entity "utm_content" not defined and no default entity

    …r&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Games Begi

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

64. Line 1761, Column 110: reference not terminated by REFC delimiter

    …m=banner&utm_source=main&utm_content=en" title="Let the Games Begin!"><img sr

    ✉

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

65. Line 1761, Column 110: reference to external entity in attribute value

    …m=banner&utm_source=main&utm_content=en" title="Let the Games Begin!"><img sr

    ✉

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

66. Line 1761, Column 110: reference to entity "utm_content" for which no system identifier could be generated

    …m=banner&utm_source=main&utm_content=en" title="Let the Games Begin!"><img sr

    ✉

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

67. Line 1761, Column 97: entity was defined here

    …eer&utm_medium=banner&utm_source=main&utm_content=en" title="Let the Games Be

68. Line 1761, Column 192: required attribute "alt" not specified

    …fx/00/27/93/storenewen_92d-aT.jpg" /></a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

69. Line 1786, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
70. Line 1786, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
71. Line 1858, Column 167: required attribute "alt" not specified

    …deo--11---day-6_50imgGalTh-fg.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

72. Line 1904, Column 229: required attribute "alt" not specified

    …ics-leaderboard_24imgGalTh-we.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

73. Line 1950, Column 233: required attribute "alt" not specified

    …remains-popular_00imgGalTh-Cq.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

74. Line 2046, Column 107: required attribute "alt" not specified

    …0/09/57/culture_42imgGalTh-ch.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

75. Line 2087, Column 158: required attribute "alt" not specified

    …g/00/09/57/code_46imgGalTh-bA.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

76. Line 2142, Column 202: required attribute "alt" not specified

    …chromeobigjpeg1_58imgGalTh-jn.jpg" />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

77. Line 2147, Column 142: character "&amp;" is the first character of a delimiter but occurred as data

    …ck-gemayel_279998ua.html"><strong>Q & A with Chromeo’s P-Thugg aka Patrick Ge

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
78. Line 2200, Column 353: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Vancouver 2010 </a><br /><a href="http:

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

79. Line 2200, Column 542: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Cultural Olympiad</a></div>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

80. Line 2201, Column 300: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Vancouver 2010</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

81. Line 2202, Column 148: required attribute "alt" not specified

    …vertical-align:middle !important;" /> Torch Relay</a><br />

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

82. Line 2203, Column 142: required attribute "alt" not specified

    …vertical-align:middle !important;" /> CODE 2010</a>

    ✉

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

83. Line 2228, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
84. Line 2228, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

    ✉

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
85. Line 2342, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

86. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

87. Line 2356, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

88. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

89. Line 2370, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

90. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

91. Line 2384, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

92. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

93. Line 2398, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

94. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

95. Line 2412, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

96. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

97. Line 2426, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

98. Line 2308, Column 17: ID "x" first defined here

             <tr id="x">

99. Line 2440, Column 17: ID "x" already defined

    								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

100. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

101. Line 2454, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

102. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

103. Line 2468, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

104. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

105. Line 2491, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

106. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

107. Line 2505, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

108. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

109. Line 2519, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

110. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

111. Line 2533, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

112. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

113. Line 2547, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

114. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

115. Line 2561, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

116. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

117. Line 2575, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

118. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

119. Line 2589, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

120. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

121. Line 2603, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

122. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

123. Line 2617, Column 17: ID "x" already defined

     								<tr id="x" onclick="switchUrl('/olympic-medals/medallists/index_ct-hX.ht

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

124. Line 2308, Column 17: ID "x" first defined here

              <tr id="x">

125. Line 2634, Column 14: end tag for "tbody" which is not finished

     						</tbody>

     ✉

     Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

     Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.

126. Line 2657, Column 120: Attribute "target" exists, but can not be used for this element.

     …this widget on your website" target="_top"><img src="/gfx/00/27/06/widgetmeda

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

127. Line 2657, Column 182: required attribute "alt" not specified

     …7/06/widgetmedalsembed_86d-JB.gif" /></a></span>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

128. Line 2695, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

       if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
129. Line 2695, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

       if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
130. Line 2720, Column 9: required attribute "type" not specified

     		<style>

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

131. Line 2720, Column 9: document type does not allow element "style" here

     		<style>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

132. Line 2728, Column 12: Attribute "name" exists, but can not be used for this element.

     <form name="#">

     ✉

     You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

     This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

     How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

133. Line 2728, Column 15: required attribute "action" not specified

     <form name="#">

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

134. Line 2729, Column 172: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

     …lue) location.href = selectedValue;">

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

135. Line 2732, Column 71: cannot generate system identifier for general entity "cat1"

     …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

136. Line 2732, Column 71: general entity "cat1" not defined and no default entity

     …guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation A

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

137. Line 2732, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

138. Line 2732, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

139. Line 2732, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alert

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

140. Line 2732, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

141. Line 2732, Column 83: cannot generate system identifier for general entity "q"

     …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

142. Line 2732, Column 83: general entity "q" not defined and no default entity

     …/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

143. Line 2732, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

144. Line 2732, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

145. Line 2732, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

146. Line 2732, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

147. Line 2732, Column 86: cannot generate system identifier for general entity "start"

     …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

     Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

     If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

     Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

148. Line 2732, Column 86: general entity "start" not defined and no default entity

     …dex_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

149. Line 2732, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

150. Line 2732, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

151. Line 2732, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

152. Line 2732, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

153. Line 2733, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

154. Line 2733, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

155. Line 2733, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alert

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

156. Line 2732, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

157. Line 2733, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

158. Line 2733, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

159. Line 2733, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</opti…

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

160. Line 2732, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

161. Line 2733, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

162. Line 2733, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

163. Line 2733, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

164. Line 2732, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

165. Line 2734, Column 75: reference not terminated by REFC delimiter

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

166. Line 2734, Column 75: reference to external entity in attribute value

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

167. Line 2734, Column 75: reference to entity "cat1" for which no system identifier could be generated

     …e/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</op

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

168. Line 2732, Column 69: entity was defined here

     …r-guide/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation

169. Line 2734, Column 84: reference not terminated by REFC delimiter

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

170. Line 2734, Column 84: reference to external entity in attribute value

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

171. Line 2734, Column 84: reference to entity "q" for which no system identifier could be generated

     …index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

172. Line 2732, Column 81: entity was defined here

     …ts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opt

173. Line 2734, Column 91: reference not terminated by REFC delimiter

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

174. Line 2734, Column 91: reference to external entity in attribute value

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

175. Line 2734, Column 91: reference to entity "start" for which no system identifier could be generated

     …f-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>

     ✉

     This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

176. Line 2732, Column 84: entity was defined here

     …index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</opti…

177. Line 2949, Column 15: required attribute "action" not specified

     <form name="#">

     ✉

     The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

     Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

178. Line 2950, Column 13: ID "drp_filter" already defined

     <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

     ✉

     An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

179. Line 2729, Column 12: ID "drp_filter" first defined here

     <select id="drp_filter" name="drp_filter drp_nojs" onchange="var selectedValue =

180. Line 2950, Column 231: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag

     …h: 280px !important; color:#0076CC;">

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

181. Line 2952, Column 3: "DOCTYPE" declaration not allowed in instance

     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

182. Line 2953, Column 43: document type does not allow element "html" here

     <html xmlns="http://www.w3.org/1999/xhtml">

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

183. Line 2959, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Albania  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

184. Line 2960, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Albania  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

185. Line 2961, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Algeria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

186. Line 2962, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Algeria  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

187. Line 2963, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Andorra  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

188. Line 2964, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Andorra  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

189. Line 2965, Column 65: document type does not allow element "option" here

     …="http://www.ar.terra.com/deportes/vancouver2010/" >Argentina - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

190. Line 2966, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Armenia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

191. Line 2967, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Armenia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

192. Line 2968, Column 42: document type does not allow element "option" here

     <option value="http://www.nos.nl/os2010" >Aruba - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

193. Line 2969, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Aruba  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

194. Line 2970, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Aruba - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

195. Line 2971, Column 56: document type does not allow element "option" here

     <option value="http://www.foxtel.com.au/vancouver2010" >Australia - Foxtel</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

196. Line 2972, Column 49: document type does not allow element "option" here

     <option value="http://ninemsn.com.au/vancouver" >Australia - Nine</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

197. Line 2973, Column 48: document type does not allow element "option" here

     <option value="http://de.eurosport.yahoo.com " >Austria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

198. Line 2974, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Austria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

199. Line 2975, Column 37: document type does not allow element "option" here

     <option value="http://sport.orf.at" >Austria - ORF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

200. Line 2976, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Azerbaijan  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

201. Line 2977, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Azerbaijan  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

202. Line 2978, Column 44: document type does not allow element "option" here

     <option value="http://olimpicgames.tvr.by" >Belarus -TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

203. Line 2979, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Belarus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

204. Line 2980, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Belarus - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

205. Line 2981, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Belgium  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

206. Line 2982, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Belgium - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

207. Line 2983, Column 42: document type does not allow element "option" here

     <option value="http://www.rtbf.be/sport" >Belgium - RTBF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

208. Line 2984, Column 76: document type does not allow element "option" here

     …/cm/sporza/ander_nieuws/Vancouver_2010" >Belgium - VRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

209. Line 2985, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Bosnia and Herzegovina</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

210. Line 2986, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Bosnia and Herzegovina - Eurovision</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

211. Line 2987, Column 60: document type does not allow element "option" here

     <option value="http://esportes.terra.com.br/vancouver2010" >Brazil - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

212. Line 2988, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >British Indian Ocean Territory</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

213. Line 2989, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >British Indian Ocean Territory  - Eurovi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

214. Line 2990, Column 38: document type does not allow element "option" here

     <option value="http://winter.bnt.bg" >Bulgaria - BNT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

215. Line 2991, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Bulgaria  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

216. Line 2992, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Bulgaria - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

217. Line 2993, Column 43: document type does not allow element "option" here

     <option value="http://www.ctvolympics.ca" >Canada - CTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

218. Line 2994, Column 45: document type does not allow element "option" here

     <option value="http://www.rdsolympiques.ca" >Canada - RDS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

219. Line 2995, Column 51: document type does not allow element "option" here

     <option value="http://www.rtve.es/vancouver-2010" >Canary Islands - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

220. Line 2996, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Canary Islands  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

221. Line 2997, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Canary Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

222. Line 2998, Column 65: document type does not allow element "option" here

     …="http://www.cl.terra.com/deportes/vancouver2010/" >Chile - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

223. Line 2999, Column 39: document type does not allow element "option" here

     <option value="http://sports.cntv.cn" >China, People's Republic of - CCTV</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

224. Line 3000, Column 57: document type does not allow element "option" here

     <option value="http://www.elta.tv/event/Vancouver2010/" >Chinese Taipei - ELTA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

225. Line 3001, Column 65: document type does not allow element "option" here

     …="http://www.co.terra.com/deportes/vancouver2010/" >Colombia - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

226. Line 3002, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Costa Rica - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

227. Line 3003, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Croatia  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

228. Line 3004, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Croatia  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

229. Line 3005, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Cyprus  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

230. Line 3006, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Cyprus  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

231. Line 3007, Column 45: document type does not allow element "option" here

     <option value="http://www.ceskatelevize.cz" >Czech Republic - ceskatelevize</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

232. Line 3008, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Czech Republic  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

233. Line 3009, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Czech Republic - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

234. Line 3010, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Denmark  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

235. Line 3011, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Denmark - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

236. Line 3012, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Denmark - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

237. Line 3013, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Denmark - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

238. Line 3014, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Dominican Republic</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

239. Line 3015, Column 65: document type does not allow element "option" here

     …="http://www.ec.terra.com/deportes/vancouver2010/" >Ecuador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

240. Line 3016, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Egypt  - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

241. Line 3017, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Egypt  - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

242. Line 3018, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >El Salvador - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

243. Line 3019, Column 39: document type does not allow element "option" here

     <option value="http://www.err.ee/om/" >Estonia - ERR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

244. Line 3020, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Estonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

245. Line 3021, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Estonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

246. Line 3022, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Falkland Islands (Malvinas)  - Eurosport

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

247. Line 3023, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Falkland Islands (Malvinas) - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

248. Line 3024, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Faroe Islands - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

249. Line 3025, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Faroe Islands - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

250. Line 3026, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Faroe Islands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

251. Line 3027, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Faroe Islands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

252. Line 3028, Column 31: document type does not allow element "option" here

     <option value="http://yle.fi" >Finland - YLE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

253. Line 3029, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Finland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

254. Line 3030, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Finland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

255. Line 3031, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >France - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

256. Line 3032, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.fr " >France - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

257. Line 3033, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >France - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

258. Line 3034, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Guyana - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

259. Line 3035, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >French Guyana - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

260. Line 3036, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >French Guyana - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

261. Line 3037, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Polynesia - France Télévisions</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

262. Line 3038, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >French Polynesia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

263. Line 3039, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >French Polynesia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

264. Line 3040, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >French Southern Territories  - France Té

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

265. Line 3041, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >French Southern Territories - Eurosport<

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

266. Line 3042, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >French Southern Territories - Eurovision

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

267. Line 3043, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Georgia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

268. Line 3044, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Georgia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

269. Line 3045, Column 48: document type does not allow element "option" here

     <option value="http://de.eurosport.yahoo.com " >Germany - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

270. Line 3046, Column 39: document type does not allow element "option" here

     <option value="http://olympia.ard.de" >Germany - ARD</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

271. Line 3047, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Germany - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

272. Line 3048, Column 39: document type does not allow element "option" here

     <option value="http://olympia.zdf.de" >Germany - ZDF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

273. Line 3049, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >Gibraltar - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

274. Line 3050, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Gibraltar - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

275. Line 3051, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Gibraltar - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

276. Line 3052, Column 56: document type does not allow element "option" here

     <option value="http://news.ert.gr/sports/olympics2010" >Greece - ERT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

277. Line 3053, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Greece - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

278. Line 3054, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Greece - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

279. Line 3055, Column 42: document type does not allow element "option" here

     <option value="http://www.dr.dk/sporten" >Greenland - DR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

280. Line 3056, Column 42: document type does not allow element "option" here

     <option value="http://www.ol2010.tv2.dk" >Greenland - TV2</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

281. Line 3057, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Greenland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

282. Line 3058, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Greenland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

283. Line 3059, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Guadeloupe - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

284. Line 3060, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Guadeloupe - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

285. Line 3061, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Guadeloupe - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

286. Line 3062, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Guatemala - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

287. Line 3063, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Honduras - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

288. Line 3064, Column 40: document type does not allow element "option" here

     <option value="http://www.i-cable.com" >Hong Kong - i-Cable</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

289. Line 3065, Column 43: document type does not allow element "option" here

     <option value="http://www.teliolimpia.hu" >Hungary - Magyar</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

290. Line 3066, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Hungary - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

291. Line 3067, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Hungary - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

292. Line 3068, Column 42: document type does not allow element "option" here

     <option value="http://www.ruv.is/ol2010" >Iceland - RUV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

293. Line 3069, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Iceland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

294. Line 3070, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Iceland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

295. Line 3071, Column 47: document type does not allow element "option" here

     <option value="http://uk.eurosport.yahoo.com" >Ireland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

296. Line 3072, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Ireland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

297. Line 3073, Column 45: document type does not allow element "option" here

     <option value="http://www.iba.org.il/sport" >Israel - IBA</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

298. Line 3074, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Israel - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

299. Line 3075, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Israel - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

300. Line 3076, Column 49: document type does not allow element "option" here

     <option value="http://www.vancouver2010.rai.it" >Italy - Rai</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

301. Line 3077, Column 45: document type does not allow element "option" here

     <option value="http://www.sky.it/olimpiadi" >Italy - Sky Italia</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

302. Line 3078, Column 37: document type does not allow element "option" here

     <option value="http://www.gorin.jp" >Japan - Gorin</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

303. Line 3079, Column 47: document type does not allow element "option" here

     <option value="http://www.nhk.or.jp/olympic " >Japan - NHK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

304. Line 3080, Column 44: document type does not allow element "option" here

     <option value="http://www.nhk-ondemand.jp" >Japan - NHK On Demand</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

305. Line 3081, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Jordan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

306. Line 3082, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Jordan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

307. Line 3083, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Kazakhstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

308. Line 3084, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Kazakhstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

309. Line 3085, Column 42: document type does not allow element "option" here

     <option value="http://olympic.sbs.co.kr" >Korea - SBS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

310. Line 3086, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Kyrgyzstan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

311. Line 3087, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Kyrgyzstan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

312. Line 3088, Column 36: document type does not allow element "option" here

     <option value="http://www.ltv7.lv" >Latvia - LTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

313. Line 3089, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Latvia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

314. Line 3090, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Latvia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

315. Line 3091, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Lebanon - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

316. Line 3092, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Lebanon - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

317. Line 3093, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Libya - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

318. Line 3094, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Libya - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

319. Line 3095, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Liechtenstein - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

320. Line 3096, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Liechtenstein - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

321. Line 3097, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Lithuania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

322. Line 3098, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Lithuania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

323. Line 3099, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Luxembourg - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

324. Line 3100, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Luxembourg - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

325. Line 3101, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Macedonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

326. Line 3102, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Macedonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

327. Line 3103, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Madeira - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

328. Line 3104, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Madeira - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

329. Line 3105, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Malta - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

330. Line 3106, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Malta - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

331. Line 3107, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Martinique - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

332. Line 3108, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Martinique - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

333. Line 3109, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Martinique - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

334. Line 3110, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >Mayotte - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

335. Line 3111, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Mayotte - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

336. Line 3112, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Mayotte - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

337. Line 3113, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Mexico - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

338. Line 3114, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Moldova, Republic Of - Eurosport</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

339. Line 3115, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Moldova, Republic Of - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

340. Line 3116, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Monaco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

341. Line 3117, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Monaco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

342. Line 3118, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Montenegro - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

343. Line 3119, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Montenegro - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

344. Line 3120, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Morocco - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

345. Line 3121, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Morroco - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

346. Line 3122, Column 38: document type does not allow element "option" here

     <option value="http://nos.nl/os2010" >Netherlands - NOS</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

347. Line 3123, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Netherlands - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

348. Line 3124, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Netherlands - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

349. Line 3125, Column 42: document type does not allow element "option" here

     <option value="http://www.nos.nl/os2010" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

350. Line 3126, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Netherlands Antilles</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

351. Line 3127, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Netherlands Antilles - Eurovision</opti…

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

352. Line 3128, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >New Caledonia - France Télévisions</opti

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

353. Line 3129, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >New Caledonia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

354. Line 3130, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >New Caledonia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

355. Line 3131, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Nicaragua - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

356. Line 3132, Column 38: document type does not allow element "option" here

     <option value="http://www.nrk.no/ol" >Norway - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

357. Line 3133, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Norway - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

358. Line 3134, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Norway - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

359. Line 3135, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Panama - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

360. Line 3136, Column 65: document type does not allow element "option" here

     …="http://www.pe.terra.com/deportes/vancouver2010/" >Peru - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

361. Line 3137, Column 45: document type does not allow element "option" here

     <option value="http://vancouver2010.tvp.pl" >Poland - TVP</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

362. Line 3138, Column 37: document type does not allow element "option" here

     <option value="http://eurosport.pl" >Poland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

363. Line 3139, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Poland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

364. Line 3140, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Portugal - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

365. Line 3141, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Portugal - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

366. Line 3142, Column 54: document type does not allow element "option" here

     <option value="http://jo-vancouver-2010.francetv.fr" >Réunion - France Télévisions</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

367. Line 3143, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Réunion - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

368. Line 3144, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Réunion - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

369. Line 3145, Column 43: document type does not allow element "option" here

     <option value="http://www.tvr.ro/Joiarna" >Romania - TVR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

370. Line 3146, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Romania - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

371. Line 3147, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Romania - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

372. Line 3148, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.ru " >Russia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

373. Line 3149, Column 41: document type does not allow element "option" here

     <option value="http://www.1tv.ru/olimp" >Russia - C1R</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

374. Line 3150, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Russia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

375. Line 3151, Column 57: document type does not allow element "option" here

     <option value="http://video.sportbox.ru/olimpiada 2010" >Russia - RTR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

376. Line 3152, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Saint Pierre And Miquelon - France Télév

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

377. Line 3153, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Saint Pierre And Miquelon - Eurosport</o

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

378. Line 3154, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Saint Pierre And Miquelon - Eurovision</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

379. Line 3155, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >San Marino - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

380. Line 3156, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >San Marino - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

381. Line 3157, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Serbia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

382. Line 3158, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Serbia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

383. Line 3159, Column 45: document type does not allow element "option" here

     <option value="http://www.stv.sk/vancouver" >Slovakia - STV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

384. Line 3160, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Slovakia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

385. Line 3161, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Slovakia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

386. Line 3162, Column 45: document type does not allow element "option" here

     <option value="http://www.rtvslo.si/oi2010" >Slovenia - RTV</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

387. Line 3163, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Slovenia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

388. Line 3164, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Slovenia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

389. Line 3165, Column 51: document type does not allow element "option" here

     <option value="http://www.rtve.es/vancouver-2010" >Spain - RTVE</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

390. Line 3166, Column 48: document type does not allow element "option" here

     <option value="http://es.eurosport.yahoo.com " >Spain - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

391. Line 3167, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Spain - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

392. Line 3168, Column 41: document type does not allow element "option" here

     <option value="http://www.nrksport.net" >Spitsbergen - NRK</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

393. Line 3169, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Spitsbergen - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

394. Line 3170, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Spitsbergen - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

395. Line 3171, Column 38: document type does not allow element "option" here

     <option value="http://www.svt.se/os" >Sweden - SVT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

396. Line 3172, Column 38: document type does not allow element "option" here

     <option value="http://eurosport.se " >Sweden - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

397. Line 3173, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Sweden - Eurovision </option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

398. Line 3174, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Switzerland - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

399. Line 3175, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Switzerland - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

400. Line 3176, Column 45: document type does not allow element "option" here

     <option value="http://www.rsi.ch/vancouver" >Switzerland - RSI</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

401. Line 3177, Column 44: document type does not allow element "option" here

     <option value="http://vancouver2010.sf.tv" >Switzerland - SF</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

402. Line 3178, Column 54: document type does not allow element "option" here

     <option value="http://www.tsrsport.ch/vancouver2010" >Switzerland - TSR</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

403. Line 3179, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Tajikistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

404. Line 3180, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Tajikistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

405. Line 3181, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >The Azores - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

406. Line 3182, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >The Azores - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

407. Line 3183, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Tunisia - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

408. Line 3184, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Tunisia - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

409. Line 3185, Column 39: document type does not allow element "option" here

     <option value="http://www.trt.net.tr" >Turkey - TRT</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

410. Line 3186, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Turkey - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

411. Line 3187, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Turkey - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

412. Line 3188, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Turkmenistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

413. Line 3189, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Turkmenistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

414. Line 3190, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Ukraine - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

415. Line 3191, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Ukraine - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

416. Line 3192, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >United Kingdom - BBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

417. Line 3193, Column 47: document type does not allow element "option" here

     <option value="http://uk.eurosport.yahoo.com" >United Kingdom - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

418. Line 3194, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >United Kingdom - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

419. Line 3195, Column 65: document type does not allow element "option" here

     …="http://www.mx.terra.com/deportes/vancouver2010/" >Uruguay - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

420. Line 3196, Column 44: document type does not allow element "option" here

     <option value="http://www.nbcolympics.com" >USA - NBC</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

421. Line 3197, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Uzbekistan - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

422. Line 3198, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Uzbekistan - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

423. Line 3199, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Vatican City State (Holy See) - Eurospor

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

424. Line 3200, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Vatican City State (Holy See) - Eurovisi

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

425. Line 3201, Column 65: document type does not allow element "option" here

     …="http://www.ve.terra.com/deportes/vancouver2010/" >Venezuela - Terra</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

426. Line 3202, Column 44: document type does not allow element "option" here

     <option value="http://www.bbc.co.uk/sport" >Virgin Islands, British</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

427. Line 3203, Column 44: document type does not allow element "option" here

     … value="http://eurosport.yahoo.com" >Virgin Islands, British - Eurosport</opt

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

428. Line 3204, Column 57: document type does not allow element "option" here

     …//www.eurovisionsports.tv/olympics" >Virgin Islands, British - Eurovision</op

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

429. Line 3205, Column 54: document type does not allow element "option" here

     …tp://jo-vancouver-2010.francetv.fr" >Wallis And Futuna - France Télévisions</

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

430. Line 3206, Column 44: document type does not allow element "option" here

     <option value="http://eurosport.yahoo.com" >Wallis And Futuna - Eurosport</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

431. Line 3207, Column 57: document type does not allow element "option" here

     <option value="http://www.eurovisionsports.tv/olympics" >Wallis And Futuna - Eurovision</option>

     ✉

     The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

     One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

432. Line 3208, Column 9: end tag for "body" omitted, but OMITTAG NO was specified

     </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

433. Line 2958: start tag was here

     ><body>

434. Line 3208, Column 9: end tag for "html" omitted, but OMITTAG NO was specified

     </select>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

435. Line 2953: start tag was here

     ><html xmlns="http://www.w3.org/1999/xhtml">

436. Line 3309, Column 99: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …nternational Olympic Committee" rel=nofollow><img src="/gfx/00/17/22/ioc_18d-

     ✉

437. Line 3310, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …apore Youth Olympic Games 2010" rel=nofollow><img src="/gfx/00/13/35/singapor

     ✉

438. Line 3311, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …et="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-2

     ✉

439. Line 3312, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …get="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-20

     ✉

440. Line 3313, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     …arget="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18/99/rio2016_

     ✉

441. Line 3383, Column 5: document type does not allow element "ul" here; assuming missing "li" start-tag

      <ul><br />

     ✉

442. Line 3383, Column 11: document type does not allow element "br" here; assuming missing "li" start-tag

      <ul><br />

     ✉

443. Line 3385, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

      <li><a href="/more-2010-information/olympic-torch-relay/olympic-torch-relay-int

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

444. Line 3390, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag

      <li><a href="/more-2010-information/olympic-torch-relay/about-the-olympic-torch

     ✉

     The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

     One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

445. Line 3391, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

446. Line 3383, Column 5: start tag was here

      <ul><br />

447. Line 3391, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

448. Line 3383, Column 1: start tag was here

      <ul><br />

449. Line 3391, Column 7: end tag for "li" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

450. Line 3383, Column 1: start tag was here

      <ul><br />

451. Line 3391, Column 7: end tag for "ul" omitted, but OMITTAG NO was specified

      </div>

     ✉

     You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

452. Line 3379, Column 1: start tag was here

      <ul>

453. Line 3422, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

454. Line 3461, Column 36: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
455. Line 3461, Column 37: character "&amp;" is the first character of a delimiter but occurred as data

      if (!(typeof nad === "undefined") && !nad)

     ✉

     This message may appear in several cases:

     • You tried to include the "<" character in your page: you should escape it as "&lt;"
     • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
     • Another possibility is that you forgot to close quotes in a previous tag.
456. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

457. Line 169, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …d = document.location.protocol == "https:";    if (!nad) document.write(unesc…

     ✉

458. Line 244, Column 30: XML Parsing Error: AttValue: " or ' expected

     document.writeln('<style type=\"text/css\">');

     ✉

459. Line 244, Column 30: XML Parsing Error: attributes construct error

     document.writeln('<style type=\"text/css\">');

     ✉

460. Line 244, Column 30: XML Parsing Error: Couldn't find end of Start Tag style line 244

     document.writeln('<style type=\"text/css\">');

     ✉

461. Line 247, Column 26: XML Parsing Error: Opening and ending tag mismatch: script line 199 and style

     document.writeln('</style>');

     ✉

462. Line 248, Column 9: XML Parsing Error: Opening and ending tag mismatch: meta line 24 and script

     </script>

     ✉

463. Line 1012, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

464. Line 1012, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …/schedule---results/" title="Schedule & Results">Schedule & Results</a></li>…

     ✉

465. Line 1123, Column 27: XML Parsing Error: AttValue: " or ' expected

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

466. Line 1123, Column 27: XML Parsing Error: attributes construct error

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

467. Line 1123, Column 27: XML Parsing Error: Couldn't find end of Start Tag div line 1123

     document.write("<div style=\"position:relative; height: 293px;\"><div style=\"po

     ✉

468. Line 1123, Column 76: XML Parsing Error: AttValue: " or ' expected

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

469. Line 1123, Column 76: XML Parsing Error: attributes construct error

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

470. Line 1123, Column 76: XML Parsing Error: Couldn't find end of Start Tag div line 1123

     …on:relative; height: 293px;\"><div style=\"position:absolute; left: -19px;\">");

     ✉

471. Line 1139, Column 22: XML Parsing Error: Opening and ending tag mismatch: script line 1116 and div

     document.write("</div></div>");

     ✉

472. Line 1145, Column 9: XML Parsing Error: Opening and ending tag mismatch: div line 1059 and script

     </script>

     ✉

473. Line 1761, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …/store/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" 

     ✉

474. Line 1761, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" title=…

     ✉

475. Line 1761, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …/?utm_campaign=cheer&utm_medium=banner&utm_source=main&utm_content=en" title=…

     ✉

476. Line 1786, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

477. Line 1786, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

478. Line 2147, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

     …festivals-and-events/news/q-a-with-chromeo's-p-thugg-aka-patrick-gemayel_2799…

     ✉

479. Line 2228, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

480. Line 2228, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

481. Line 2695, Column 37: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

482. Line 2695, Column 38: XML Parsing Error: xmlParseEntityRef: no name

       if (!(typeof nad === "undefined") && !nad)

     ✉

483. Line 2732, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Aler

     ✉

484. Line 2732, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

485. Line 2732, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199826&q=&start=1" >Transportation Alerts</op…

     ✉

486. Line 2733, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Aler

     ✉

487. Line 2733, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

488. Line 2733, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199828&q=&start=1" >Event Schedule Alerts</op…

     ✉

489. Line 2734, Column 74: XML Parsing Error: EntityRef: expecting ';'

     …de/alerts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</o

     ✉

490. Line 2734, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

491. Line 2734, Column > 80: XML Parsing Error: EntityRef: expecting ';'

     …rts/index_cf-Lk.html?cat6=&cat1=199834&q=&start=1" >Ticketing Alerts</option>…

     ✉

492. Line 2952, Column 1: XML Parsing Error: StartTag: invalid element name

     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.or

     ✉

493. Line 3208, Column 9: XML Parsing Error: Opening and ending tag mismatch: body line 2958 and select

     </select>

     ✉

494. Line 3209, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2953 and form

     </form>

     ✉

495. Line 3210, Column 6: XML Parsing Error: Opening and ending tag mismatch: select line 2950 and div

     </div>

     ✉

496. Line 3211, Column > 80: XML Parsing Error: Opening and ending tag mismatch: form line 2949 and div

     …line" src="/gfx/00/23/57/broadcaster2_00d-ku.jpg" /></div>…

     ✉

497. Line 3309, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

498. Line 3309, Column > 80: XML Parsing Error: attributes construct error

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

499. Line 3309, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3309

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

500. Line 3309, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3309 and a

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

501. Line 3309, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3308 and li

     …t="_blank" title="International Olympic Committee" rel=nofollow><img src="/gf…

     ✉

502. Line 3310, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

503. Line 3310, Column > 80: XML Parsing Error: attributes construct error

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

504. Line 3310, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3310

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

505. Line 3310, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3310 and a

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

506. Line 3310, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3306 and li

     …target="_blank" title="Singapore Youth Olympic Games 2010" rel=nofollow><img …

     ✉

507. Line 3311, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

508. Line 3311, Column > 80: XML Parsing Error: attributes construct error

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

509. Line 3311, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3311

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

510. Line 3311, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3311 and a

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

511. Line 3311, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3305 and li

     …get="_blank" title="London 2012" rel=nofollow><img src="/gfx/00/17/22/london-…

     ✉

512. Line 3312, Column 76: XML Parsing Error: AttValue: " or ' expected

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

513. Line 3312, Column 76: XML Parsing Error: attributes construct error

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

514. Line 3312, Column 76: XML Parsing Error: Couldn't find end of Start Tag a line 3312

     …rget="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2

     ✉

515. Line 3312, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3312 and a

     …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

516. Line 3312, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 3288 and li

     …="_blank" title="Sochi 2014" rel=nofollow><img src="/gfx/00/17/22/sochi-2014_…

     ✉

517. Line 3313, Column > 80: XML Parsing Error: AttValue: " or ' expected

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

518. Line 3313, Column > 80: XML Parsing Error: attributes construct error

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

519. Line 3313, Column > 80: XML Parsing Error: Couldn't find end of Start Tag a line 3313

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

520. Line 3313, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 3313 and a

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

521. Line 3313, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 275 and li

     …ault.aspx" target="_blank" title="Rio 2016" rel=nofollow><img src="/gfx/00/18…

     ✉

522. Line 3314, Column 6: XML Parsing Error: Opening and ending tag mismatch: div line 274 and ul

      </ul>

     ✉

523. Line 3391, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 3383 and div

      </div>

     ✉

524. Line 3410, Column 8: XML Parsing Error: Opening and ending tag mismatch: ul line 3379 and div

     		</div><!-- end of refLine -->

     ✉

525. Line 3422, Column 58: XML Parsing Error: AttValue: " or ' expected

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

526. Line 3422, Column 58: XML Parsing Error: attributes construct error

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

527. Line 3422, Column 58: XML Parsing Error: Couldn't find end of Start Tag a line 3422

     			<li><a href="/olympic-news/rss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

528. Line 3422, Column 74: XML Parsing Error: Opening and ending tag mismatch: li line 3422 and a

     …ss-feeds/" title="RSS" rel=nofollow>RSS</a></li>

     ✉

529. Line 3422, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 3414 and li

     … title="RSS" rel=nofollow>RSS</a></li>…

     ✉

530. Line 3423, Column 5: XML Parsing Error: Opening and ending tag mismatch: div line 3413 and ul

     </ul>

     ✉

531. Line 3430, Column 7: XML Parsing Error: Opening and ending tag mismatch: body line 263 and div

      </div>

     ✉

532. Line 3449, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and div

     	</div><!--end of wrapFooter-->

     ✉

533. Line 3460, Column 2: XML Parsing Error: Extra content at the end of the document

     		<script type="text/javascript">

     ✉

↑ Top